===============================================================
 How to link TimbyrNode to Dlubal RFEM 6
===============================================================

TimbyrNode imports member geometry and forces directly from an
RFEM 6 model over Dlubal's API. You need:

  1. An RFEM 6 API key, saved in a file next to TimbyrNode.exe
  2. RFEM 6 running, with your model open and results calculated
  3. An RFEM version that matches your TimbyrNode build


---------------------------------------------------------------
 1. Get your API key (in your Dlubal account, NOT inside RFEM)
---------------------------------------------------------------

  1. Go to www.dlubal.com, sign in, and open "My Account".
  2. Open the "API & Cloud" tab.
  3. In the left-hand menu, under "API II", click "My API Keys".
  4. Click "Create New API Key" and copy the key (it looks like
     "ak-...").

Keep the key private; it is tied to your Dlubal account.


---------------------------------------------------------------
 2. Save it as RFEM6_API_key.txt
---------------------------------------------------------------

Create a plain text file named exactly

    RFEM6_API_key.txt

in the SAME folder as TimbyrNode.exe, with the key on the FIRST
line. Lines starting with "#" are ignored, so you can keep a note
in the file. If you ever regenerate the key, update this file.


---------------------------------------------------------------
 3. Before you import
---------------------------------------------------------------

When you press Connect in TimbyrNode's RFEM import:

  - RFEM 6 must be RUNNING, with your model OPEN.
  - The ULS load combinations must be CALCULATED in RFEM;
    TimbyrNode imports forces from calculated results.

TimbyrNode opens a short connection and closes it again, so RFEM
is only busy for a moment.


---------------------------------------------------------------
 4. Version compatibility
---------------------------------------------------------------

Dlubal updates the RFEM API frequently, so each TimbyrNode build
is matched to a specific RFEM 6 version, shown at the top of the
RFEM import dialog.

  - Different RFEM version: member FORCES still import correctly,
    but cross-section sizes and material may not be read
    automatically; enter them in the mapping table. TimbyrNode
    shows a short caution when this happens.
  - A read fails outright: update RFEM or TimbyrNode so the two
    match, or contact us with your exact RFEM version (for
    example 6.15.0005).


---------------------------------------------------------------
 Troubleshooting
---------------------------------------------------------------

  - "No RFEM API key found": sections 1 and 2.
  - "Could not connect to RFEM 6" / "Could not read the RFEM
    model": RFEM running, model open, results calculated? Then
    press Connect again.
  - A caution about the RFEM version: section 4.
  - Still stuck: email us a screenshot and your exact RFEM
    version.

    support@timbyrnode.com
